Re: [INTERFACES] Proper use of Transactions...

At 23:38 +0300 on 08/08/1999, Matthew Hagerty wrote:


> All this is compounded because I am using PHP3 as an Apache module to
> access PostgreSQL and I am receiving the following error in my Apache log:
>
> NOTICE:  (transaction aborted): queries ignored until END
>
> I'm not sure where to start looking for the problem.  Any insight would be
> greatly appreciated.

This is just normal. It indicates that since an error has occured, the rest
of the commands in the transaction, if they are issued, will be ignored -
untill you say either "commit" or "rollback". It gives you the effect of
not doing anything more in a transaction if an error occured in the middle
of it.

If errors which are not database errors occur in the middle (for example,
you run a validity test on the user's data and it fails), you should catch
those errors and issue a rollback yourself.

This has nothing to do with the type of interface you are using (in your
case PHP3), unless that interface does not allow you to make validity tests
or to capture errors. I don't think there is damage to the database if a
transaction is not committed or rolled back before the connection
terminates - but a guru opinion would have more value than mine.

Herouth

--
Herouth Maoz, Internet developer.
Open University of Israel - Telem project
http://telem.openu.ac.il/~herutma